Trouble Shooting

This page will provide information to help solve several common problems that users encounter when using MaxCrypt. If you need help solving a problem or would like to report a bug, you can email us at info@kinocode.com.

I’m unable to login to MaxCrypt.

If MaxCrypt reports that either your login name or password is incorrect, then there are a couple things you can do. First, be sure that your caps lock is off. Both the password and login name are case sensitive.

You can test your login name and password by using the “Diagnostic” function of the Emergency Rescue program. You will be prompted to select an encrypted file and then to enter your login name and password. If the password is correct, but the login name is not, the program will give you the correct login name. If the password is incorrect, then it can not be recovered.

I uninstalled MaxCrypt and now I have encrypted files left on my computer.

All files should have been removed from user encryption lists before uninstalling. If you still have encrypted files on your hard disk, use the Emergency Rescue program to search your hard disks for files and then enter your login name and password to recover the files.

I have forgotten my login name and or password.

If you have forgotten your login name, then it can be recovered using the Emergency Rescue program. If you have lost your password, then there isn’t anything that can be done to recover it.

You can recover your login name by using the “Diagnostic” function of the Emergency Rescue program. You will be prompted to select an encrypted file and then to enter your login name and password. If you have no idea what the login name is, just enter anything. If the password is correct, but the login name is not, the program will give you the correct login name.

After installing MaxCrypt, the restart command in Windows shuts the computer down, but does not restart.

This is a known bug. MaxCrypt needs to intercept Windows shutdown to encrypt files, but Windows does not give any information on whether the user was trying to shutdown or restart. This bug will not be fixed until version 2.0 when intercepting Windows shutdown will no longer be necessary.